Mobile device as a security system component

ABSTRACT

In one implementation, a method for using a mobile computing device as a security system component includes receiving, from a mobile device and by a security system gateway, mobile device sensor information associated with sensor data captured by the mobile device at a premises monitored by the security system gateway; identifying, based on the received sensor information, a mobile device sensor information rule; identifying an action to perform in the mobile device sensor information rule; and automatically performing the identified action, by the security system gateway, in response to receiving the sensor information from the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit of the U.S. patent application Ser. No.17/038,449, filed on Sep. 30, 2020, which claims priority to U.S.Provisional Patent Application No. 62/908,046, filed on Sep. 30, 2019,and is incorporated herein by reference.

TECHNICAL FIELD

This specification generally relates to security systems.

BACKGROUND

Security systems have included sensors and other security systemcomponents that transmit signals to a security system controller, suchas a security control panel and/or gateway device, that processes thesignals and determines whether to generate a security alarm, or othersecurity-related notification. Such sensors and other peripheral devicescan transmit signals over wired and/or wireless connections with thesecurity system controller. For example, in a wireless security system,distributed sensors can wirelessly communicate when a state of thesensor has changed, such as a reed switch that has changed state due toa door being opened. In addition, wireless sensors may communicate withthe control panel on a periodic basis making what is typically called a“supervisory” transmission, for example, to communicate that the sensoris working properly and that its battery is satisfactory. Depending onthe state of the control panel (for example, whether in an “armed state”or not), the security system controller can determine whether the stateinformation provided to it by the sensors constitutes an alarmcondition, and if so, the controller can be programmed to take theappropriate action, such as sounding a siren, making communications to aremote monitoring system, etc.

SUMMARY

This document is generally directed to security systems in which ageneral purpose mobile computing device, such as a smartphone, acts as asecurity system component providing input to a security systemcontroller to assess the state of a premises and to determine whether totake one or more actions (e.g., sounding a siren, generating an alarm).For example, general purpose mobile computing devices have beenconnected to and used as part of security systems to output securitysystem information to users (e.g., output security system statusinformation) and to provide user interfaces through which users cancontrol security systems (e.g., output user interface through which thesecurity system can be armed/disarmed). However, in such contextsgeneral purpose mobile computing devices have not provided informationsensed locally by the mobile computing devices on conditions related tothe premises where the security system is located (e.g., home, business,building). Yet, mobile computing devices include a variety of onboardsensors and other components that can be used to readily determineconditions in and around where they are currently located, such assensors (e.g., temperature sensors, motion sensors, light sensors,accelerometers, tilt sensors, proximity sensors), cameras (e.g., frontfacing cameras, rear facing cameras), microphones, location detectingcomponents (e.g., GPS units, local wireless signal-based locationdetermination units), wireless signal detection components (e.g., Wi-Fichipset, BLUETOOTH chipset), and/or other components. This document isgenerally directed to using information indicating local conditions ator around a premises that is detected/determined by onboard componentsin a mobile computing device as input to a security system, in additionto and/or instead of premises information provided by security sensorsand other security system components.

For instance, when a mobile device is located at a premises, it cantransmit sensor information to the security controller at the premises,such as a security gateway. For example, a mobile computing device cantransmit audio signals that can be analyzed by the security controllerto determine whether a loud noise occurs, such as a window breaking. Thesecurity controller can be programmed to generate security alarms and/orother alerts in response to such events occurring, such as transmittingnotifications to mobile computing devices associated with the premisesthat a loud noise was detected, sounding a siren, and/or transmittingalarm conditions. In another example, a mobile computing device cantransmit information identifying nearby detected wireless devices (e.g.,wireless signals received with at least a minimum threshold signalstrength), which can be used by the security system controller todetermine whether any foreign/unknown mobile devices are at or near thepremises, which may be an indication of an intruder or unknown person atthe premises. In another example, a mobile computing device can transmita video stream from one or more cameras, which can be used by thesecurity system to determine the state/condition of the premisesthrough, for instance, the use of object detection and machine learningalgorithms (e.g., detect whether windows and doors are open or closedthrough optical object recognition). In another example, a mobilecomputing device can transmit temperature information to a securitycontroller, which may be used to determine whether alerts should begenerated indicating, for instance, that a door has been left ajarand/or that HVAC equipment may be malfunctioning. Additional and/orother information detected by onboard components within a mobilecomputing device can be transmitted and used by a security system toassess conditions at a premises, and/or other use cases are alsopossible.

Mobile computing devices can act in any of a variety of modes, such as asensor mode in which they are transmitting information on conditions ator near a premises to a security system controller, an interface mode inwhich they are providing information on conditions in the premisesand/or control features for controlling the security system, a dualsensor-interface mode in which they are simultaneously acting in boththe sensor mode and the interface mode, security controller mode inwhich they act as a security system controller, dual securitycontroller-sensor modes in which they are simultaneously acting as boththe security system controller and sensor modes, triple securitycontroller-sensor-interface modes in which they act in all three of thecontroller, sensor, and interface modes, and/or other modes (orcombinations thereof).

Security system controllers can be local at a premises and/or remotefrom the premises. For example, in some instances, a security systemcontroller can be a device that is located at a premises and with whicha mobile computing device can communicate over a local communicationnetwork (e.g., Wi-Fi network, BLUETOOTH network). In some instances, thesecurity system controller can be a remote device and/or system, such asa cloud-based computer system with which a mobile computing devicecommunicates over one or more wide area networks (e.g., internet, mobiledata network, virtual private network). Other configurations of asecurity system controller are also possible, such as a combination of alocal device and a remote system that collectively provide controllerfeatures.

In some instances, the mobile computing device can, itself, perform theoperations of a security system controller, which may be performed inaddition to the mobile computing device using its onboard components todetect conditions at or around a premises. In such instances, the mobilecomputing device may also receive information from sensors and othersecurity system components on conditions in or around a premises. Forexample, a mobile computing device can be used to provide a mobilesecurity system that can be transported with a user and setup, with oneor more mobile sensors, to secure a perimeter at a new/temporarylocation, such as a hotel room and/or other temporary lodgingaccommodation. For instance, a user staying in a hotel room can placedoor and window sensors on the doors and windows in a hotel room thatwirelessly transmit state information (e.g., open state, close state) tothe mobile computing device, which can act as a security systemcontroller for the premises. The mobile computing device canadditionally act as a sensor in such a situation, providing informationon conditions in the premises using the onboard components of the mobilecomputing device.

Such features can be provided on mobile computing devices, for example,through downloadable applications that can be installed on the devices(e.g., mobile apps). Such applications may access information from oneor more onboard components on the mobile computing devices, as permittedby the device's onboard security and privacy restrictions, which may beapproved and/or adjusted by the device's user. Such mobile applicationsmay, in some instances, process some or all information from onboardcomponents before transmission to a security system controller foranalysis. In some instances, mobile applications can transmit a streamof information obtained by onboard components of a mobile computingdevice. Other configurations are also possible.

Systems, methods and techniques are described herein. In oneimplementation, a method for using a mobile computing device as asecurity system component includes receiving, from a mobile device andby a security system gateway, mobile device sensor informationassociated with sensor data captured by the mobile device at a premisesmonitored by the security system gateway; identifying, based on thereceived sensor information, a mobile device sensor information rule;identifying an action to perform in the mobile device sensor informationrule; and automatically performing the identified action, by thesecurity system gateway, in response to receiving the sensor informationfrom the mobile device.

Such a method can optionally include one or more of the followingfeatures. The mobile device sensor information can be the sensor datacaptured by the mobile device. The mobile device sensor information caninclude information generated by the mobile device processing the sensordata captured by the mobile device. The method can further includedetermining, by the security system gateway, that the mobile device isat the premises and wherein the mobile device sensor information rule isidentified in response to determining that the mobile device is at thepremises. The security system gateway can determine that the mobiledevice is at the premises based on location information sent by themobile device along with the mobile device sensor information. Thesecurity system gateway can determine that the mobile device is at thepremises based on evaluating a signal strength of a signal from themobile device that includes the mobile device sensor information. Therule can specify that the mobile device is to be located at thepremises. The action can include generating an alarm. The mobile devicesensor information can include one or more of temperature information,motion detection, camera images, captured video, or captured audio.

In another implementation, method for using a mobile computing device asa security system component includes determining, by a security systemgateway, that the security system gateway is not capable of wide areanetwork communication; sending a backup connection request, to a mobiledevice, for the mobile device to act as a wide area network backupconnection for the security system gateway; receiving a response, fromthe mobile device, to the backup connection request, confirming that themobile device will act as the wide area network backup connection;creating a message targeted for a remote security system service;sending the message to the mobile device with a forwarding request forthe message to be sent to the remote security system service by themobile device on behalf of the security system gateway; and receiving aconfirmation, from the mobile device, that the message has been sent tothe remote security system service, by the mobile device, on behalf ofthe security system gateway.

Such a method can optionally include one or more of the followingfeatures. The backup connection request can be sent to the mobile deviceover a local area network connection. The mobile device can send themessage over a wide area network. The method can further includereceiving, from the mobile device, a reply message that was sent to themobile device from the remote security system service, in reply to themessage. The reply message can be sent to the mobile device over a widearea network connection. The reply message can be received by thegateway over a local area network connection.

In another implementation, a system includes a mobile device; and one ormore local sensors local to a premises; wherein the mobile device isconfigured as a security system gateway for the premises and wherein themobile device is configured to: receive information from the one or morelocal sensors; identify a security system rule based on the receivedinformation; identify an action in the identified security system rule;and automatically perform the identified action.

Such a system can optionally include one or more of the followingfeatures. The mobile device can be configured to generate sensorinformation for the premises using one or more mobile device sensors ofthe mobile device. The mobile device can be configured to identify thesecurity system rule based on the sensor information for the premisesgenerated using the one or more mobile device sensors and theinformation from the one or more local sensors.

Certain implementations may provide one or more advantages. For example,A mobile device can be used as a sensor for providing information to asecurity system for evaluation and action. A mobile device can be usedas a backup communication connection for a security system. A mobiledevice can be used as a security system gateway.

The details of one or more implementations of the subject matterdescribed in this specification are set forth in the accompanyingdrawings and the description below. Other features, aspects, andadvantages of the subject matter will become apparent from thedescription, the drawings, and the claims.

BRIEF DESCRIPTION OF THE ATTACHMENTS

FIG. 1 is a block diagram of an example security system environment.

FIGS. 2-7 are conceptual diagrams illustrating examples of using amobile device as a security system component.

FIG. 8 depicts a flowchart of an example technique for using a mobiledevice as a security system component.

FIG. 9 is a block diagram of an example security system environment.

FIG. 10 depicts a flowchart of an example technique for using a mobiledevice as a backup communication connection for a security system.

FIG. 11 is a block diagram of an example security system environment.

FIG. 12 is a conceptual diagram illustrating using a mobile device as asecurity system gateway.

FIG. 13 depicts a flowchart of an example technique for using a mobiledevice as a security system gateway.

FIG. 14 is a block diagram of an example computer system that can beused to implement the methods, systems and processes described in thisdisclosure.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

This document describes systems, devices, techniques, and mechanisms forsecurity systems in which a mobile device can be used as a securitysystem component. For instance, a mobile device can be used as a sensorfor providing information to a security system, as a backupcommunication connection for a security system, and/or as a securitysystem gateway.

FIG. 1 is a block diagram showing interactions within an examplesecurity system. For example, the security system can include a securitysystem premises gateway (e.g., a gateway 100) and related components.The example gateway 100 can control the security system and can providean interface for a mobile computing device 102 to access/control thesecurity system. Mobile devices 102 can include, for example, generalpurpose mobile control devices, including smart phones, tablet computingdevices, laptop computers, wearable computing devices, and/or othercomputing devices that may be mobile. Other types of computing devicescan be used as the mobile device 102. The gateway 100 can communicatewith other components, including security system detectors 106, a remotesecurity system service 112, and security system control devices (notshown).

Communications among the gateway 100 and related components can includelocal area network (LAN) communications 114 and wide area network (WAN)communications 116. LAN communications 114 can be used, for example,among components that are situated in the premises of the gateway 100,including the mobile device 102, when present within a thresholddistance of the gateway 100 (e.g., in or near the home or otherbuilding(s) in which the gateway 100 is located). Components thatcommunicate over the LAN can include LAN communication systems 118(peripheral role) and 120 (central role), and a cellular communicationsystem 122 (e.g., WAN). Security system-related components can use astandard security system communication system 124 (e.g., using standardsecurity system transmissions 125). WAN communication between thegateway 100 and the mobile device can be handled using a WANcommunication system network 126 (e.g., that services cellular phonenetworks). In some implementations, communication between the gateway100 and the mobile device 102 can be handled with a downloaded securitysystem control application 134.

The mobile device 102 can include a variety of sensors. The securitysystem control application 134 can obtain sensor information generatedor gathered by sensors of the mobile device 102 and provide the sensorinformation to the gateway 100. The mobile device 102 includes, forexample, a temperature sensor 140, a GPS (Global Positioning Satellite)receiver 142, an accelerometer 144, a gyroscope 146, a camera 148, aproximity sensor 150, an ambient light sensor 152, a compass 154, abarometer 156, a microphone 158, and a fingerprint scanner 160. Thesecurity system control application 134 can obtain information fromthese and other sensors and provide sensor information to the gateway100. In some implementations, the mobile device 102 provides sensorinformation to the gateway 100 without processing the sensorinformation. In other examples, the security system control application134 may analyze sensor information and determine which sensorinformation (or which analysis information) to provide to the gateway100 (e.g., based on a set of rules).

The gateway 100 can identify, based on the received sensor information,a mobile device sensor information rule 140 (e.g., from among multipleconfigured rules). The mobile device sensor information rule 140 canspecify an action to perform when certain type(s) (or certain values) ofmobile device sensor information is received. The gateway 100 canautomatically perform the identified action, in response to receivingthe sensor information from the mobile device 102. Actions can include,for example, generating an alert or alarm, automatically arming ordisarming the security system, or otherwise configuring the securitysystem.

FIG. 2 is a conceptual diagram illustrating an example of using a mobiledevice as a security system component. A mobile device 201 runs anapplication that is configured to send temperature readings measured bythe mobile device 201 to a security system gateway 202 in a home 204.The application may be configured to send temperature readingsperiodically (e.g., every minute) or only if a read temperature is morethan a predetermined threshold temperature, for example. A user of themobile device 201 may start the application before going to bed atnight, or may leave the mobile device 201 at the home 204 when leavingthe home 204, for example.

The mobile device 201 is placed within a room 206. The mobile device hasmeasured a temperature of the room as 170 degrees, e.g., due to a fire208 that has started in the room 206. The measured temperature of 170degrees may be more than a threshold temperature of 150 degrees forexample. Accordingly, the mobile device 201 can send temperatureinformation 210 to the gateway 202. As another example, in some casesthe presence of an intruder may cause an increase in the ambienttemperature of the room 206 which can trigger sending of temperatureinformation from the mobile device 201 to the gateway 202.

The gateway 202 can perform one or more actions in response to receivingthe temperature information 210. For example, the gateway 202 canautomatically generate one or more alerts or alarms, automatically senda message to a mobile device of an owner of the home 204, automaticallysend a message to emergency responder(s), etc. The gateway 202 maydetermine to perform an action based on the received temperatureinformation 210 and on other received or determined information. Forexample, the security system itself may include or be connected to othertemperature sensors which have provided temperature information to thegateway 202. As another example, non-standard security devices in thehome 204, such as personal computers or other smart appliances may haveprovided temperature information to the gateway 202.

FIG. 3 is a conceptual diagram illustrating another example of using amobile device as a security system component. A mobile device 301 runsan application that is configured to record audio and send recordedaudio (or information about the recorded audio) to a security systemgateway 302 in a home 304. The application may be configured to sendrecorded audio if a detected decibel level is more than a predeterminedthreshold decibel level, for example. A user of the mobile device 301may start the application before going to bed at night, or may leave themobile device 301 at the home 304 when leaving the home 304, forexample. The mobile device 301 is placed within a room 306 underneath awindow 308. If an intruder attempts to break into the home 304 bybreaking the window 308, the application can detect that audio of awindow breakage 310 is more than a predefined decibel level, and cansend recorded audio 312 (or an indication that detected audio is morethan the predefined decibel level) to the gateway 302.

The gateway 302 can be configured to perform one or more actions inresponse to receiving audio or audio-related information from the mobiledevice 301. For instance, if the gateway 302 receives an indication thataudio more than the threshold decibel level has been detected by themobile device 301, the gateway 302 can generate one or more alerts oralarms, send a message to a remote security service, send a message toanother mobile device of the user (e.g., that may be with the user whenthe user is not at the home 304), etc. In some implementations, themobile device 301 application performs analysis of recorded audio andsends information about the analysis to the gateway 302. For instance,the application can determine that recorded audio sufficiently matches atemplate sound of a window breakage, and the mobile device 301 can sendan indication that a window breakage has been detected to the gateway302. The gateway 302 can automatically perform one or more actions basedon a type of received audio-analysis information. For instance, thegateway 302 can generate an on-premise alarm if the gateway 302 receivesan indication that a window breakage has been detected.

As another example, the mobile device 301 can send recorded audio to thegateway 302 (e.g., when noise(s) more than a threshold decibel levelhave been detected), and the gateway 302 can analyze the received audio.The gateway 302 can analyze received audio and determine that thereceived audio sufficiently matches a template sound of a windowbreakage. The gateway 302 can automatically perform an action (e.g.,generating an alarm) based on determining that received audio matchesone of a predetermined set of audio types (e.g., window breakage, gunshot, door slam, human scream or human voices, etc.).

FIG. 4 is a conceptual diagram illustrating another example of using amobile device as a security system component. A mobile deviceapplication can be configured to send information to a security systemgateway when the application has determined that a mobile device is ator in proximity to the same premises monitored by the gateway. Asanother example, the gateway can determine a location of a mobiledevice, such as by triangulating signals received from the mobiledevice, and determine whether the mobile device is at or in proximity tothe premises. If the mobile device is at or in proximity to thepremises, the gateway can consider (and potentially act on) informationreceived from the mobile device. If the mobile device is not at thepremises (e.g., as determined by a particularly weak signal from themobile device), the gateway may discard or downgrade informationreceived from the mobile device. In some implementations, the mobiledevice sends location information along with other sensor-relatedinformation. The gateway can determine, based on the received locationinformation, whether the mobile device is at the premises monitored bythe gateway, with the gateway acting accordingly to received mobiledevice information based on whether the mobile device is present.

For example, an owner of a home 402 that is monitored by a gateway 404may be leaving the premises, with a mobile device 406, in a car 407. Asecurity application that was running when the user was at the home 402may still be running on the mobile device 406, recording audio,determining whether recorded audio is greater than a threshold decibellevel, or performing other actions. For instance, the mobile deviceapplication may detect noise from a car horn 408 and determine that thecar horn noise is greater than a predetermined decibel level. The mobiledevice application, before sending audio to the gateway 404, maydetermine a location of the mobile device 406. If the mobile deviceapplication determines that the mobile device 406 is not at or inproximity to the home 404, the mobile device application may determineto not send recorded audio. The mobile device application may determineto stop security monitoring (e.g., stop the application or put theapplication in a non-monitoring mode, stop recording audio) based ondetermining that the mobile device 406 is not at the premises.

In some implementations, if the mobile device application is performingsecurity monitoring, the mobile device application sends sensor-relatedinformation to the gateway 402 without checking a location of the mobiledevice 406. For instance, the mobile device 406 can send car horn audio410 (or information indicating a car horn sound) to the gateway 404. Thegateway 404 can receive the car horn audio 410 (or audio information)and can determine a location of the mobile device 406 (e.g., either bytriangulating signal information received from the mobile device 406 orevaluating location information received from the mobile device 406).The gateway 404 can, for example, determine that the mobile device 406is no longer at or near the home 404, and accordingly ignore thereceived car horn audio (or audio information). The gateway 404 canstore location information 412 for the mobile device 406, and use thestored location information in the future, such as if the gateway 404can't determine a subsequent location of the mobile device 406 to pairwith other information received from the mobile device 406.

FIG. 5 is a conceptual diagram illustrating another example of using amobile device as a security system component. In some implementations, amobile device and/or a gateway 501 can be configured to ignore ordowngrade information received from certain locations within a monitoredpremises. Or, as another example, the mobile device and/or the gateway501 can be configured to ignore or downgrade information received fromcertain locations within a monitored premises when other conditions arepresent, such as an owner being home or a current time being inpreconfigured time windows. As yet another example, the mobile deviceand/or gateway 501 can be configured to ignore or discard certain typesof detected signals.

For instance, a user 502 has just parked a car 504 in a garage 506 at ahome 508, and is shutting a garage door 510 of the garage 506. Asecurity application running on a mobile device 512 of the user 502 candetect and record a garage-door-closing noise 514. In someimplementations, the mobile device 502 sends garage-door-closing audio516 to the gateway 501, for evaluation by the gateway 501. In otherexample, the mobile device application performs processing beforesending (or deciding whether to send) the garage-door-closing audio 516.

The mobile device application and/or the gateway 501 can be configuredto ignore certain types of audio, or, in some examples, certain types ofaudio occurring at certain times, or certain types of audio occurring atcertain times when the user 502 is at the home 508. For instance, themobile device application and/or the gateway 501 can be configured toignore garage-door closing audio when the user 502 is home, or ignoregarage-door-closing audio when the user 502 is home and a current timeis outside of the hours of 12:00 am to 6:00 am. As yet another example,the mobile device application and/or the gateway 501 can be configuredto ignore garage-door-closing audio when the mobile device 512 islocated within the garage 506 (e.g., either the mobile deviceapplication or the gateway 501 can determine a location of the mobiledevice 512 within or near the home 508). The gateway 501 can determineand maintain location information 516 for the mobile device 502, forexample.

FIG. 6 is a conceptual diagram illustrating another example of using amobile device as a security system component. A user of a securitysystem places a mobile device 601 in a window 602 (e.g., on the insideof the window glass) of a home 604, and establishes a connection betweenthe mobile device 601 and a gateway 606 that is located within the home604. The user may place the mobile device 601 in the window 602 todetect movement of the window 602 (e.g., when the user is away from thehome 604, at home sleeping, etc.). The mobile device 601 can beconfigured to run an application that uses a gyroscope and/or anaccelerometer of the mobile device 601 to detect movement (e.g.,opening, breakage) of the window 602. The mobile device 601 may befastened to the window 602, e.g., by using fasteners or by being placedin a cradle, so that if the window 602 is opened (or the glass aroundthe mobile device 601 is broken), the mobile device 601 will move andthe application will detect the movement. The application can beconfigured to send a movement detection notification 608 to the gateway606, upon detection of movement of the mobile device 601.

The gateway 606 can perform one or more actions upon receiving anindication of motion detection. For instance, the gateway 606 can send anotification to the user (e.g., to another mobile device that is withthe user), send a message to a remote security system service, generatean on-premises alarm, or perform some other action.

FIG. 7 is a conceptual diagram illustrating another example of using amobile device as a security system component. A user of a securitysystem places a mobile device 701 in a window 702 (e.g., on the insideof the glass) of a home 704, and establishes a connection between themobile device 701 and a gateway that is located within the home 704. Theuser may place the mobile device 701 in the window 702 to detectmovement outside the home 704 when the user is away from the home 704.The mobile device 701 can be configured to run an application thatcaptures video in a field of view 706 of a camera of the mobile device701. The application can be configured to detect motion (e.g., a changein captured video frames) and send a notification to the gateway whenmotion is detected. For instance, a person 708 approaching the home 704while the user is away can be detected by the application on the mobiledevice 701 and the mobile device 701 can send an indication of detectedmovement to the gateway.

The gateway can perform one or more actions upon receiving an indicationof motion detection. For instance, the gateway can send a notificationto the user (e.g., to another mobile device that is with the user), senda message to a remote security system service, generate an alarm, orperform some other action. In some implementations, the mobile devicesends captured video to the gateway and the gateway sends the capturedvideo to the remote security service, to enable the user to view thecaptured video. The captured video can include a predefined number ofseconds of video before motion detection and after motion detectionends, for example.

FIG. 8 depicts a flowchart of an example technique 800 for using amobile device as a security system component.

At 802, a security system gateway receives, from a mobile device, mobiledevice sensor information associated with sensor data captured by themobile device at a premises monitored by the security system gateway.

At 804, a mobile device sensor information rule is identified, based onthe received sensor information.

At 806, an action to perform in response to the received mobile devicesensor information is identified, in the mobile device sensorinformation rule.

At 808, the security system gateway automatically performs theidentified action, in response to receiving the sensor information fromthe mobile device.

FIG. 9 is a block diagram of an example security system environment. Thegateway 100 can determine that WAN transmission 116 with the WANcommunication system network 126 is not possible, e.g., as illustratedby a broken communication link 902. The gateway 100 may have attemptedWAN communication, without success, or may have detected a conditionwhereby the gateway 100 is otherwise aware that WAN communications bythe gateway 100 are not currently possible. For instance, the cellularcommunication system 122 may be malfunctioning or inoperative.

After determining that WAN communication by the gateway 100 is notcurrently possible, the gateway 100 can send a backup connection request904, to the mobile device 102, for the mobile device 102 to act as a WANbackup connection for the gateway 100. The backup connection request 904can be sent as a LAN transmission 114, using the LAN communicationsystem 120, for example. The mobile device 102 can send a response tothe backup connection request 904 to the gateway 100 (e.g., confirmingthat the mobile device 102 can act as a WAN backup connection for thegateway 100).

The gateway 100, when needing to send a WAN message (e.g., targeted tothe remote security system service 112), can send a message 906 to themobile device 102, e.g., with a forwarding request for the message 906to be sent to the remote security system service 112 by the mobiledevice 102 on behalf of the gateway 100. The mobile device 102 can senda forwarded message 908, as a WAN transmission 116, over the WANcommunication system network 126, to the remote security system service112. The remote security system service 112 can receive a forwardedmessage 910, over the WAN communication system network 126. The mobiledevice 102 can send a confirmation message, to the gateway 100,indicating that that the message 906 has been sent to the remotesecurity system service 112, by the mobile device 102, on behalf of thegateway 100.

FIG. 10 depicts a flowchart of an example technique 1000 for using amobile device as a backup communication connection for a securitysystem. At 1002, the gateway 100 attempts WAN communication over the WANcommunication systems network 126 (e.g., the gateway 100 may attempt WANcommunication with the remote security system service 112 or withanother system or service). The attempted communication fails, asindicated by a no-communications symbol 1004. As another example, thegateway 100 can otherwise determine that communication over the WANcommunication system network 126 may fail or is otherwise not possible.For instance, at 1006, the gateway 100 determines a failure of theattempted WAN communication.

At 1008, in response to determining that WAN communication by thegateway 100 is not possible, the gateway 100 sends a backup WANconnection request to the mobile device 102, e.g., over a LANconnection, for the mobile device 102 to act as a backup WANcommunication system/connection that the gateway 100 can use to accessthe WAN communication system network 126. At 1010, the mobile device 102receives the backup WAN connection request.

At 1012, the mobile device 102 confirms an ability to perform WANcommunications on the WAN communication system network 126. Forinstance, at 1014, the WAN communication system network 126 and themobile device 102 may perform a communication handshake to verify anability for the mobile device 102 to send WAN communications.

At 1016, the mobile device 102 sends a confirmation message to thegateway 100 confirming the backup WAN connection request (e.g.,confirming that the mobile device 102 can act as a backup communicationsystem for the gateway 100). At 1018, the gateway 100 receives theconfirmation message from the mobile device 102.

At 1020, the gateway 100 generates a message targeted to the remotesecurity system service 112 and forwards the targeted message to themobile device 102, as a request for the mobile device 102 to send thetargeted message to the remote security system service as a WAN message,on behalf of the gateway 100. At 1022, the mobile device 102 receivesthe targeted message. At 1024, the mobile device 102 sends the targetedmessage over the WAN communication system network 126, targeted for theremote security system service 112. At 1026, the WAN communicationsystem network 126 receives the targeted message from the mobile device102. At 1028, the message is provided, over the WAN communication systemnetwork 126, to the remote security system service 112. Although notshown, the remote security system service 112 can send a reply message,over the WAN communication system network 126, to the mobile device 102,and the mobile device 102 can forward the reply message, over a LANconnection, to the gateway 100.

FIG. 11 is a block diagram of an example security system environment.The mobile device 102 can be used as security system gateway, forexample, when a user is at a remote location other than a locationmonitored by the gateway 100. The security system control application134 (or another application) can perform security monitoring at theremote location, using information obtained by sensors 1102 of themobile device 102, and information obtained from other devices at theremote location, such as security system detectors 106 and/or IoT(Internet of Things) devices 1104.

IoT devices 1104 can include components in the remote location that mayor may not be security system-related, such as temperature sensors andcontrols (including heating and air conditioning), doors, locks, garagedoors, appliances, lights, and other systems. In some implementations,the IoT devices 1104 can be part of an IoT device ecosystem 1106 at theremote location. In some implementations, the IoT devices 1104 can becontrolled and/or interfaced with an IoT ecosystem gateway 1108.

The mobile device 102 can analyze generated and received information,identify rules that match the generated and/or received information,including identifying one or more actions, and automatically perform theone or more actions. For instance, the mobile device 102 can emit analarm noise at the remote location, or send a message to actuate analarm device external to the mobile device 102 that is at the remotelocation. In some examples, the mobile device 102 can communicate withthe remote security system service 112 when performing an action (e.g.,to request that the remote security system service 112 contact firstresponders). As another example, the mobile device 102 can send amessage to the gateway 100 requesting that the gateway 100 perform anaction. For instance, the mobile device 102 can request that the gateway100 contact the remote security system service 112, e.g., as a redundantrequest or if the mobile device 102 has detected a failed attempt atcommunication with the remote security system service 112. As anotherexample, the mobile device 102 may be monitoring an adjacent location toa location monitored by the gateway 100, and the mobile device 102 cansend a message to the gateway 100 for the gateway 100 to generate analarm at the location monitored by the gateway. For instance, thegateway 100 may be monitoring a home and the mobile device 102 may bemonitoring an outdoor shed or barn.

FIG. 12 is a conceptual diagram illustrating using a mobile device as asecurity system gateway. A user staying in a room 1200 (e.g., a hotelroom or another temporary dwelling) uses a mobile device 1202 as asecurity system gateway. For example, the mobile device 1202 cancommunicate with other devices in the room 1200, to implement a securitysystem that secures the room 1200. The mobile device 1202 can useinformation gathered by the mobile device 1202, and information gatheredor obtained by other devices in the room 1200, to implement the securitysystem.

For instance, the mobile device 1202 can be placed on a dresser 1203 inthe room 1200 so that a camera of the mobile device 1202 has a field ofview 1204 that includes a door 1206. The user can place the mobiledevice 1202 on the dresser 1203 when going to sleep and/or can place themobile device 1202 on the dresser 1203 when leaving the room 1200, forexample. An application running on the mobile device 1202 can detectmotion within the field of view 1204, for example. The mobile device1202 can perform one or more actions in response to detected motion,such as generating an audio alarm on the mobile device 1202 or onanother connected device, or sending a message to one or more devices orsystems (e.g., to another device of the user, to a hotel front desk, topolice, to a remote security system service, etc.). In someimplementations, the mobile device application sends a message to asecurity system gateway installed in a regular (e.g., permanent) home ofthe user, requesting that the security system gateway perform one ormore actions. For instance, the mobile device 1202 can send a message toan in-home security system gateway requesting that the security systemgateway send a message to a remote security system monitoring service.

In addition to using information obtained by the mobile device 1202, themobile device 1202 can process information received from other devicesin the room 1200. For instance, switch sensors 1208 and 1210 have beenplaced on the door 1206 to detect opening of the door 1206. The switchsensors 1208 and 1210 can send a message to the mobile device 1202 whenopening of the door 1206 is detected. In response to receiving a messageregarding opening of the door 1206, the mobile device 1202 canautomatically perform one or more actions, as described above. As asimilar example, switch sensors 1212 and 1214 and switch sensors 1216and 1218, have been placed on windows 1220 and 1222, respectively. Anyof the switch sensors 1212, 1214, 1216, or 1218 can send a messageregarding opening of a respective window 1220 or 1222, to the mobiledevice 1202. In response to receiving a message regarding opening of thewindow 1220 or the window 1222, the mobile device 1202 can automaticallyperform one or more actions, as described above.

As another example, a camera 1224 can detect motion within a field ofview 1226, with the field of view 1226 including the window 1220 and thewindow 1222. The user can use the camera 1224 to detect motion withinthe field of view 1226, since the camera of the mobile device 1202 maynot be able to capture both the door 1206 and the windows 1220 and 1222.Other than the camera 1224, the user can use a second mobile device (notshown) to detect motion from opening of the windows 1220 and 1222. Thecamera 1224 (or the second mobile device) can send captured video (or anindication of detected motion) to the mobile device 1202. The mobiledevice 1202 can automatically perform one or more actions, in responseto determining, from information received from the camera 1224 (or thesecond mobile device), that motion has been detected by the window 1220or the window 1222.

If a second mobile device is used, the mobile device 1202 can beconfigured as a master mobile device and the second mobile device can beconfigured as an auxiliary (e.g., secondary) mobile device, for example.The mobile device 1202 and the second mobile device can run a same ordifferent security application, for example. If running a same securityapplication, the mobile device 1202 can run in a master mode and thesecond mobile device can run in an auxiliary mode.

As yet another example, the mobile device application running on themobile device 1202 can detect when the mobile device 1202 is moved(e.g., picked up by an intruder or an unauthorized/unexpected personother than the user). For instance, the mobile device application candetect when information from a gyroscope and/or an accelerometer of themobile device 1202 indicates movement of the mobile device 1202. Inresponse to detecting unauthorized or unexpected movement of the mobiledevice 1202, the mobile device application can automatically perform oneor more actions, such as generating an alarm or sending a message to oneor more devices or systems. The user can unlock the mobile device 1202without generation of an alarm by entering in a code without moving themobile device 1202 while the mobile device 1202 is in a cradle, forexample.

In addition to devices and sensors shown, the mobile device 1202 canreceive and act on information from other devices or systems. Forexample, other devices in the room 1200 can record audio, temperature,barometric pressure, smoke levels, or other information, and providerecorded information to the mobile device 1202. The mobile deviceapplication can process received information, evaluate one or more rulesbased on type(s) of received information, and automatically perform oneor more actions that are specified in or associated with the evaluatedrule(s).

FIG. 13 depicts a flowchart of an example technique 1300 for using amobile device as a security system gateway. At 1302, a mobile device isconfigured as a security system gateway for a premises.

At 1304, the mobile device receives information from the one or morelocal sensors that are located at the premises.

At 1306, the mobile device identifies a security system rule based onthe received information. In some implementations, the mobile devicegenerates mobile device sensor information from one or more sensors anduses the generated sensor information (perhaps along with the receivedinformation from the local sensors) to identify the security systemrule.

At 1308, the mobile device identifies an action in the identifiedsecurity system rule.

At 1310, the mobile device automatically performs the identified action.

FIG. 14 is a block diagram of example computing devices 1400, 1450 thatmay be used to implement the systems and methods described in thisdocument, as either a client or as a server or plurality of servers.Computing device 1400 is intended to represent various forms of digitalcomputers, such as laptops, desktops, workstations, personal digitalassistants, servers, blade servers, mainframes, and other appropriatecomputers. Computing device 1400 is further intended to represent anyother typically non-mobile devices, such as televisions or otherelectronic devices with one or more processers embedded therein orattached thereto. Computing device 1450 is intended to represent variousforms of mobile devices, such as personal digital assistants, cellulartelephones, smartphones, and other computing devices. The componentsshown here, their connections and relationships, and their functions,are meant to be examples only, and are not meant to limitimplementations of the inventions described and/or claimed in thisdocument.

Computing device 1400 includes a processor 1402, memory 1404, a storagedevice 1406, a high-speed controller 1408 connecting to memory 1404 andhigh-speed expansion ports 1410, and a low-speed controller 1412connecting to low-speed bus 1414 and storage device 1406. Each of thecomponents 1402, 1404, 1406, 1408, 1410, and 1412, are interconnectedusing various busses, and may be mounted on a common motherboard or inother manners as appropriate. The processor 1402 can processinstructions for execution within the computing device 1400, includinginstructions stored in the memory 1404 or on the storage device 1406 todisplay graphical information for a GUI on an external input/outputdevice, such as display 1416 coupled to high-speed controller 1408. Inother implementations, multiple processors and/or multiple buses may beused, as appropriate, along with multiple memories and types of memory.Also, multiple computing devices 1400 may be connected, with each deviceproviding portions of the necessary operations (e.g., as a server bank,a group of blade servers, or a multi-processor system).

The memory 1404 stores information within the computing device 1400. Inone implementation, the memory 1404 is a computer-readable medium. Inone implementation, the memory 1404 is a volatile memory unit or units.In another implementation, the memory 1404 is a non-volatile memory unitor units.

The storage device 1406 is capable of providing mass storage for thecomputing device 1400. In one implementation, the storage device 1406 isa computer-readable medium. In various different implementations, thestorage device 1406 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device, a flash memory or other similarsolid state memory device, or an array of devices, including devices ina storage area network or other configurations. In one implementation, acomputer program product is tangibly embodied in an information carrier.The computer program product contains instructions that, when executed,perform one or more methods, such as those described above. Theinformation carrier is a computer- or machine-readable medium, such asthe memory 1404, the storage device 1406, or memory on processor 1402.

The high-speed controller 1408 manages bandwidth-intensive operationsfor the computing device 1400, while the low-speed controller 1412manages lower bandwidth-intensive operations. Such allocation of dutiesis an example only. In one implementation, the high-speed controller1408 is coupled to memory 1404, display 1416 (e.g., through a graphicsprocessor or accelerator), and to high-speed expansion ports 1410, whichmay accept various expansion cards (not shown). In the implementation,low-speed controller 1412 is coupled to storage device 1406 andlow-speed bus 1414. The low-speed bus 1414 (e.g., a low-speed expansionport), which may include various communication ports (e.g., USB,Bluetooth®, Ethernet, wireless Ethernet), may be coupled to one or moreinput/output devices, such as a keyboard, a pointing device, a scanner,or a networking device such as a switch or router, e.g., through anetwork adapter.

The computing device 1400 may be implemented in a number of differentforms and/or virtualized, as shown in the figure. For example, it may beimplemented as a standard server 1420, or multiple times in a group ofsuch servers. It may also be implemented as part of a rack server system1424. In addition, it may be implemented in a personal computer such asa laptop computer 1422. Alternatively, components from computing device1400 may be combined with other components in a mobile device (notshown), such as computing device 1450. Each of such devices may containone or more of computing devices 1400, 1450, and an entire system may bemade up of multiple computing devices 1400, 1450 communicating with eachother.

Computing device 1450 includes a processor 1452, memory 1464, aninput/output device such as a display 1454, a communication interface1466, and a transceiver 1468, among other components. The computingdevice 1450 may also be provided with a storage device, such as amicro-drive or other device, to provide additional storage. Each of thecomponents 1450, 1452, 1464, 1454, 1466, and 1468, are interconnectedusing various buses, and several of the components may be mounted on acommon motherboard or in other manners as appropriate.

The processor 1452 can process instructions for execution within thecomputing device 1450, including instructions stored in the memory 1464.The processor may also include separate analog and digital processors.The processor may provide, for example, for coordination of the othercomponents of the computing device 1450, such as control of userinterfaces, applications run by computing device 1450, and wirelesscommunication by computing device 1450.

Processor 1452 may communicate with a user through control interface1458 and display interface 1456 coupled to a display 1454. The display1454 may be, for example, a TFT LCD display or an OLED display, or otherappropriate display technology. The display interface 1456 may compriseappropriate circuitry for driving the display 1454 to present graphicaland other information to a user. The control interface 1458 may receivecommands from a user and convert them for submission to the processor1452. In addition, an external interface 1462 may be provided incommunication with processor 1452, so as to enable near areacommunication of computing device 1450 with other devices. Externalinterface 1462 may provide, for example, for wired communication (e.g.,via a docking procedure) or for wireless communication (e.g., viaBluetooth® or other such technologies).

The memory 1464 stores information within the computing device 1450. Inone implementation, the memory 1464 is a computer-readable medium. Inone implementation, the memory 1464 is a volatile memory unit or units.In another implementation, the memory 1464 is a non-volatile memory unitor units. Expansion memory 1474 may also be provided and connected tocomputing device 1450 through expansion interface 1472, which mayinclude, for example, a subscriber identification module (SIM) cardinterface. Such expansion memory 1474 may provide extra storage spacefor computing device 1450, or may also store applications or otherinformation for computing device 1450. Specifically, expansion memory1474 may include instructions to carry out or supplement the processesdescribed above, and may include secure information also. Thus, forexample, expansion memory 1474 may be provide as a security module forcomputing device 1450, and may be programmed with instructions thatpermit secure use of computing device 1450. In addition, secureapplications may be provided via the SIM cards, along with additionalinformation, such as placing identifying information on the SIM card ina non-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, asdiscussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 1464, expansionmemory 1474, or memory on processor 1452.

Computing device 1450 may communicate wirelessly through communicationinterface 1466, which may include digital signal processing circuitrywhere necessary. Communication interface 1466 may provide forcommunications under various modes or protocols, such as GSM voicecalls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, orGPRS, among others. Such communication may occur, for example, throughtransceiver 1468 (e.g., a radio-frequency transceiver). In addition,short-range communication may occur, such as using a Bluetooth®, WiFi,or other such transceiver (not shown). In addition, GPS receiver module1470 may provide additional wireless data to computing device 1450,which may be used as appropriate by applications running on computingdevice 1450.

Computing device 1450 may also communicate audibly using audio codec1460, which may receive spoken information from a user and convert it tousable digital information. Audio codec 1460 may likewise generateaudible sound for a user, such as through a speaker, e.g., in a handsetof computing device 1450. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, etc.) and may also include sound generated by applicationsoperating on computing device 1450.

The computing device 1450 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 1480. It may also be implemented as part of asmartphone 1482, personal digital assistant, or other mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. Other programming paradigms can be used, e.g., functionalprogramming, logical programming, or other programming. As used herein,the terms “machine-readable medium” “computer-readable medium” refers toany computer program product, apparatus and/or device (e.g., magneticdiscs, optical disks, memory, Programmable Logic Devices (PLDs)) used toprovide machine instructions and/or data to a programmable processor,including a machine-readable medium that receives machine instructionsas a machine-readable signal. The term “machine-readable signal” refersto any signal used to provide machine instructions and/or data to aprogrammable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular implementations of particularinventions. Certain features that are described in this specification inthe context of separate implementations can also be implemented incombination in a single implementation. Conversely, various featuresthat are described in the context of a single implementation can also beimplemented in multiple implementations separately or in any suitablesub-combination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular implementations of the subject matter have beendescribed. Other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results. In certain implementations, multitasking andparallel processing may be advantageous.

What is claimed is:
 1. A method for using a mobile computing device as asecurity system component, the method comprising: receiving, from amobile device and by a security system gateway, mobile device sensorinformation associated with sensor data captured by the mobile device ata premises monitored by the security system gateway; identifying, basedon the received sensor information, a mobile device sensor informationrule; identifying an action to perform in the mobile device sensorinformation rule; and automatically performing the identified action, bythe security system gateway, in response to receiving the sensorinformation from the mobile device.
 2. The method of claim 1, whereinthe mobile device sensor information is the sensor data captured by themobile device.
 3. The method of claim 1, wherein the mobile devicesensor information includes information generated by the mobile deviceprocessing the sensor data captured by the mobile device.
 4. The methodof claim 3, wherein the information generated by the mobile devicecomprises information generated from one or more sensors.
 5. The methodof claim 4, wherein the information generated from the one or moresensors comprises at least one of temperature information, motiondetection, camera images, captured video, and captured audio.
 6. Themethod of claim 1, further comprising determining, by the securitysystem gateway, that the mobile device is at the premises and whereinthe mobile device sensor information rule is identified in response todetermining that the mobile device is at the premises.
 7. The method ofclaim 6, wherein the security system gateway determines that the mobiledevice is at the premises based on location information sent by themobile device along with the mobile device sensor information.
 8. Themethod of claim 6, wherein the security system gateway determines thatthe mobile device is at the premises based on evaluating a signalstrength of a signal from the mobile device that includes the mobiledevice sensor information.
 9. The method of claim 1, wherein identifyinga mobile device sensor information rule comprises selecting a rule froma set of rules based on the received sensor information.
 10. The methodof claim 1, wherein the rule specifies that the mobile device is to belocated at the premises.
 11. The method of claim 1, wherein the actioncomprises generating an alarm.
 12. The method of claim 1, wherein themobile device sensor information includes one or more of temperatureinformation, motion detection, camera images, captured video, orcaptured audio.
 13. A system comprising: a mobile device; and one ormore local sensors local to a premises; wherein the mobile device isconfigured as a security system gateway for the premises and wherein themobile device is configured to: receive information from the one or morelocal sensors; identify a security system rule based on the receivedinformation; identify an action in the identified security system rule;and automatically perform the identified action.
 14. The system of claim13, wherein the mobile device is configured to generate sensorinformation for the premises using one or more mobile device sensors ofthe mobile device.
 15. The system of claim 14, wherein the sensorinformation comprises one or more of temperature information, motiondetection, camera images, captured video, or captured audio.
 16. Thesystem of claim 15, wherein the mobile device is configured to identifya security system rule by selecting a rule from a set of rules based onthe received information.
 17. The system of claim 14, wherein the mobiledevice is configured to identify the security system rule based on thesensor information for the premises generated using the one or moremobile device sensors and the information from the one or more localsensors.
 18. The system of claim 13, wherein the mobile device isconfigured to automatically perform the identified action by generatingan alarm.
 19. The system of claim 13, wherein the security system rulespecifies that the mobile device is to be located at the premises. 20.The system of claim 19, wherein the mobile device is further configuredto determine that the mobile device is at the premises, and wherein thesecurity system rule is identified in response to determining that themobile device is at the premises.